<?php
/**
 * <https://y.st./>
 * Copyright © 2018 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => '<code>taylor</code>',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2018/05/14.jpg" alt="The bottom of my Librem 15" class="framed-centred-image" width="649" height="480"/>
<section id="Discover">
	<h2>Discover didn&apos;t listen</h2>
	<p>
		It seems the Discover representative from a week or two ago didn&apos;t actually listen to me.
		Instead of changing my email address on file to what I specified, they changed it to a malformed address.
		The authorisation codes are still not arriving as they should, but this time, I can&apos;t rule out the possibility of it being because the website&apos;s trying to send codes to a technically-invalid email address.
		Most sites can send to addresses like that just fine, but others can&apos;t, and it&apos;s not even their fault because they&apos;re just following the rules.
		It&apos;s actually the websites that <strong>*can*</strong> send to malformed addresses that are doing things wrong.
	</p>
	<p>
		Anyway, I know for a fact that this problem isn&apos;t caused by the malformed address, as the problem <strong>*predates*</strong> the address on file being malformed.
		However, if the problem gets fixed, I may not know it, if this new problem prevents the codes from getting through as well.
		I&apos;ve had to have Discover change the email address on file <strong>*again*</strong>, so now I&apos;m going to have to wait <strong>*again*</strong> to try to get help with this issue.
	</p>
</section>
<section id="recipe">
	<h2>Recipe</h2>
	<p>
		The <a href="/en/recipe/ranch_dressing.xhtml">ranch dressing</a> recipe from last night turned out great!
		Admittedly, this batch does have a couple problems, but I&apos;m in a rush to release now because I&apos;ve now got two people waiting for it.
		I think the main issue though stems from the odd jar of vegan mayonnaise I got last time.
		It weighed about twenty grams less than the other jars I&apos;ve gotten, for no apparent reason.
		As a result, this batch had less mayo than the recipe actually called for.
		If made with the right measurements, I think this recipe will work out fine.
		Second, I&apos;m not sure if the second mixing of the ranch had an unintended and permanent thinning effect.
		I&apos;m hoping not.
		I&apos;m not sure why it thickens though.
		It could be like when you mix a jell snack: it doesn&apos;t go back to being solid.
	</p>
	<p>
		Anyway, even as thin as it is, it&apos;s great.
		I&apos;d want it thicker for the recipe, as I think others would want it slightly thicker, but for my own production, I&apos;d want it this thin anyway.
		I like thinner dressings.
	</p>
</section>
<section id="laptop">
	<h2>Librem laptop</h2>
	<p>
		The laptop arrived today.
	</p>
	<p>
		I hoped the Librem laptop to offer disk encryption.
		Purism claims to value security, so why shouldn&apos;t their operating system, PureOS, offer disk encryption?
		This is doubly true because PureOS is a fork of Debian, and Debian offers disk encryption.
		Before even starting the thing up, I found the Purism team did us one better.
		The manual told me the machine would ask for two passwords during setup, the first being the disk encryption password and the other being the user account password.
		This thing doesn&apos;t ask if you want your data encrypted - it just does it!
	</p>
	<p>
		I also noticed that the kill switch for the camera and microphone had them turned off before they even shipped the device.
		You have to specifically turn them on.
		I&apos;m probably reading more into this than I should, but I found joy in that being the default.
		It felt ... like a deliberate decision by the company.
		The Wi-Fi/Bluetooth kill toggle on the other hand, was set to allow use of wireless communications, further making the camera/microphone initial setting seem deliberate.
		I mean, what good is a general-use computer these days if it&apos;s not connected to the Internet?
	</p>
	<p>
		I set down the manual to type my observations, and when I looked at the manual again, which I&apos;d happened to set face down, I noticed the {$a['CC BY-SA']} logo.
		The manual itself is under the {$a['CC BY-SA 4.0']} license!
		That shouldn&apos;t surprise me, as the company&apos;s website is under the same license, but still, it always gives me good feelings about a company when I see real-world, physical items they&apos;ve released under free license.
	</p>
	<p>
		Back to the manual it gave me a warning that the laptop hasn&apos;t been tested on a spaceship or in a nuclear power plant, and that it isn&apos;t meant to be used in water or as a riot shield.
		Um, what?
		Okay, I get that the laptop may not function in unusual environments.
		I&apos;m not sure what space travel would do to a laptop, if anything, but nuclear radiation seems like it could be damaging.
		But water use and use as a riot shield?
		Of <strong>*course*</strong> you shouldn&apos;t be getting your computer wet or letting things get whacked against it.
		What a bizarre warning.
	</p>
	<p>
		There was the option to set up an email account during the $a[OS] setup process, but it of course required entry of the password.
		Until the machine is set up, I&apos;ll have no access to that; it&apos;s in my KeePassX database.
	</p>
	<p>
		There aren&apos;t any mouse buttons on this machine though.
		I can &quot;click&quot; by tapping, but how do I &quot;click and drag&quot;?
		I got some help from someone on $a[IRC], thankfully.
		The entire trackpad is a button; it clicks and everything.
		So pushing enough to hit that threshold, you can push and drag.
		You need to push harder than I normally do when using a touchpad, so I would&apos;ve never have noticed it without help.
		The keys are in strange places too, due to the inclusion of an actual numeric keypad section included in the keyboard.
		This&apos;ll take some getting used to.
	</p>
	<p>
		When the machine prompted me for a name, I named it <a href="/en/domains/taylor.local.xhtml"><code>taylor</code></a>, though I forgot to use the $a[FQDN] <code>taylor.hn.y.st</code>, as I&apos;d normally do on Debian.
		The machine never prompted me for a domain like Debian would have if I&apos;d forgotten to specify it as the initial name, so I guess this machine might not have a $a[FQDN] now?
		Maybe PureOS doesn&apos;t even use domains in whatever unknown way Debian does?
		I don&apos;t know.
		There&apos;s no way to get back to the setup prompts.
	</p>
	<p>
		Another interesting difference between the PureOS setup and a Debian setup is that PureOS offered me several username suggestions, where Debian just assumes a lower-case version of your given name to be your preferred user name, though you can of course correct it.
		Given my full name, &quot;Alexand(er|ra) Yst&quot;, PureOS came up with the following suggestions, defaulting to the first:
	</p>
	<ul>
		<li>
			alexanderrayst
		</li>
		<li>
			alexanderray
		</li>
		<li>
			ayst
		</li>
		<li>
			yalexanderra
		</li>
		<li>
			ysta
		</li>
		<li>
			yst
		</li>
		<li>
			alexanderra
		</li>
	</ul>
	<p>
		It&apos;s always mildly bothered me that Debian assumes the given name to be the username.
		Full name would be fine.
		I use my surname as my username, but if Debian assumed that to be the username, it&apos;d be just as odd.
		I liked to see PureOS doing this better, even though it was just a minor detail that doesn&apos;t mean a thing after the install completes (as you&apos;re able to override the default username anyway).
	</p>
</section>
<section id="humidifier">
	<h2>A humidifier?</h2>
	<p>
		It turns out the air conditioner wasn&apos;t getting fixed.
		Instead, a portable &quot;air conditioner&quot; has been brought in.
		It doesn&apos;t help though.
		The boss even thinks it might not be an air conditioner, but a humidifier.
		This is of course backed up by the fact that the large machine has a water tank that needs refilling and that several of us felt like the air was much more humid than usual.
		Who chose this thing as the &quot;air conditioner&quot; to bring in?
		Did the boss choose it without even knowing what it is?
		Or was it someone higher up?
		Why would you buy a large, ostensibly pricey machine without making sure of what it was first!?
	</p>
</section>
<section id="drudgery">
	<h2>Drudgery</h2>
	<p>
		My discussion post for the day:
	</p>
	<blockquote>
		<p>
			That inability to learn information about further out in the network is indeed a terrible problem.
			Without seeing the bigger picture, problems such as looping occur, and downed nodes don&apos;t really get dealt with properly by other nodes on the network.
			Clearly, networking architects learned from their mistakes when they made link state routing though.
			I can&apos;t really blame them for bad initial design.
			I myself sometimes have to tear apart larger projects and rebuild due to terrible design decisions made in the early stages.
			Building something helps you understand how you <strong>*should*</strong> have built it.
			You&apos;ve just got to correct your mistakes and continue on.
		</p>
	</blockquote>
</section>
END
);
